Skip to content

Conversation

@scttcper
Copy link
Member

@scttcper scttcper commented Dec 12, 2025

Allows filtering on release date added which we display as created.

example release.created:-7d

Motivation: the date filter doesn't really work this way on releases, this could be interesting?

Allows filtering on release date added which we display as created.
@scttcper scttcper requested a review from a team as a code owner December 12, 2025 19:27
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Dec 12, 2025
@scttcper scttcper requested a review from a team December 12, 2025 19:28
@scttcper scttcper changed the title feat(releases): Add release.created to release query feat(releases): Support filtering by release.created Dec 12, 2025
**{
f"date_added__{OPERATOR_TO_DJANGO[search_filter.operator]}": search_filter.value.raw_value
}
)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Missing negation handling causes KeyError with != operator

The RELEASE_CREATED_KEY filter directly accesses OPERATOR_TO_DJANGO[search_filter.operator], but OPERATOR_TO_DJANGO does not include the != operator. When a user queries with release.created:!=<date>, this will raise a KeyError. The adjacent SEMVER_BUILD_ALIAS filter correctly handles this by calling handle_operator_negation() first to convert != to = and extract a negated flag, then using exclude() when negated.

Fix in Cursor Fix in Web

**{
f"date_added__{OPERATOR_TO_DJANGO[search_filter.operator]}": search_filter.value.raw_value
}
)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Missing negation handling causes KeyError with != operator

The RELEASE_CREATED_KEY filter directly accesses OPERATOR_TO_DJANGO[search_filter.operator], but OPERATOR_TO_DJANGO does not include the != operator. When a user queries with release.created:!=<date>, this will raise a KeyError. The adjacent SEMVER_BUILD_ALIAS filter correctly handles this by calling handle_operator_negation() first to convert != to = and extract a negated flag, then using exclude() when negated.

Fix in Cursor Fix in Web

Copy link
Member

@malwilley malwilley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems useful!

@getsantry
Copy link
Contributor

getsantry bot commented Jan 3, 2026

This pull request has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you add the label WIP, I will leave it alone unless WIP is removed ... forever!


"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

@getsantry getsantry bot added the Stale label Jan 3, 2026
@scttcper scttcper merged commit 9b4b4b6 into master Jan 5, 2026
64 checks passed
@scttcper scttcper deleted the scttcper/release-created branch January 5, 2026 19:57
cathteng pushed a commit that referenced this pull request Jan 5, 2026
Allows filtering on release date added which we display as created. 

example `release.created:-7d`

Motivation: the date filter doesn't really work this way on releases,
this could be interesting?
scttcper added a commit that referenced this pull request Jan 14, 2026
Adds support for filtering on release.created that was added in #104877

<img width="379" height="267" alt="image"
src="https://github.com/user-attachments/assets/8b92ef57-6d6f-4819-aa87-2d5b79f5256f"
/>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components Stale

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants